V2X communication over multiple radio access types

ABSTRACT

Apparatuses, methods, and systems are disclosed for V2X communication over multiple radio access types. One method includes establishing, via a remote unit, multiple network connections for communication with a mobile network and multiple network connections for V2X communication with other remote units over multiple radio access types. The method includes receiving a request to transmit a V2X communication. The method includes determining whether the V2X communication is to be transmitted via a communication with a mobile network or a V2X communication with other remote units. The method includes determining a radio access type of the multiple radio access types for transmitting the V2X communication via V2X communication. The method includes selecting a cell that supports V2X resource management for the V2X communication. The method includes requesting resources via the cell for transmitting the V2X communication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No.62/654,955 entitled “METHODS FOR SUPPORTING V2X SERVICES OVER MULTIPLERADIO ACCESS TECHNOLOGIES” and filed on Apr. 9, 2018 for DimitriosKarampatsis, which is incorporated herein by reference in its entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to V2X communication overmultiple radio access types.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 4^(th) Generation (“4G”), 5^(th)Generation (“5G”), 5G System (“5GS”), Positive-Acknowledgment (“ACK”),Aggregation Level (“AL”), Access and Mobility Management Function(“AMF”), Access Network (“AN”), Access Point (“AP”), AuthenticationServer Function (“AUSF”), Beam Failure Detection (“BFD”), Binary PhaseShift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report(“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Carrier Aggregation(“CA”), Contention-Based Random Access (“CBRA”), Clear ChannelAssessment (“CCA”), Control Channel Element (“CCE”), Cyclic DelayDiversity (“CDD”), Code Division Multiple Access (“CDMA”), ControlElement (“CE”), Contention-Free Random Access (“CFRA”), Closed-Loop(“CL”), Coordinated Multipoint (“CoMP”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“CSI”), ChannelState Information-Reference Signal (“CSI-RS”), Common Search Space(“CSS”), Control Resource Set (“CORESET”), Discrete Fourier TransformSpread (“DFTS”), Downlink Control Information (“DCI”), Downlink (“DL”),Demodulation Reference Signal (“DMRS”), Data Radio Bearer (“DRB”),Discontinuous Reception (“DRX”), Downlink Pilot Time Slot (“DwPTS”),Enhanced Clear Channel Assessment (“eCCA”), EPS Connection Management(“ECM”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”),Effective Isotropic Radiated Power (“EIRP”), European TelecommunicationsStandards Institute (“ETSI”), Evolved Packet Core (“EPC”), EvolvedPacket System (“EPS”), Evolved Universal Terrestrial Access (“E-UTRA”),Evolved Universal Terrestrial Access Network (“E-UTRAN”), Frame BasedEquipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”),Frequency Division Orthogonal Cover Code (“FD-OCC”), 5G Node B or NextGeneration Node B (“gNB”), General Packet Radio Services (“GPRS”), GuardPeriod (“GP”), Global System for Mobile Communications (“GSM”), GloballyUnique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), HybridAutomatic Repeat Request (“HARQ”), Home Location Register (“HLR”), HomePLMN (“HPLMN”), Home Subscriber Server (“HSS”), Identity or Identifier(“ID”), Information Element (“IE”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Layer 2 (“L2”), Licensed Assisted Access (“LAA”), Load BasedEquipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”),Logical Channel Prioritization (“LCP”), Log-Likelihood Ratio (“LLR”),Long Term Evolution (“LTE”), Multiple Access (“MA”), Medium AccessControl (“MAC”), Multimedia Broadcast Multicast Services (“MBMS”),Modulation Coding Scheme (“MC S”), Master Information Block (“MIB”),Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”),Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”),massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine TypeCommunication (“MTC”), Multi User Shared Access (“MUSA”), Non AccessStratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or(“NAK”), Network Entity (“NE”), Network Function (“NF”), Next GenerationRAN (“NG-RAN”), Non-Orthogonal Multiple Access (“NOMA”), New Radio(“NR”), Network Repository Function (“NRF”), Network Slice Instance(“NSI”), Network Slice Selection Assistance Information (“NSSAI”),Network Slice Selection Function (“NSSF”), Network Slice SelectionPolicy (“NSSP”), Operation and Maintenance System (“OAM”), OrthogonalFrequency Division Multiplexing (“OFDM”), Open-Loop (“OL”), Other SystemInformation (“OSI”), Power Angular Spectrum (“PAS”), Physical BroadcastChannel (“PBCH”), Power Control (“PC”), LTE-to-V2X Interface (“PC5”),Primary Cell (“PCell”), Policy Control Function (“ ”PCF”), Physical CellID (“PCID”), Physical Downlink Control Channel (“PDCCH”), Packet DataConvergence Protocol (“PDCP”), Physical Downlink Shared Channel(“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit(“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom(“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), PublicLand Mobile Network (“PLMN”), Physical Random Access Channel (“PRACH”),Physical Resource Block (“PRB”), Primary Secondary Cell (“PSCell”),Physical Uplink Control Channel (“PUCCH”), Physical Uplink SharedChannel (“PUSCH”), Quasi Co-Located (“QCL”), Quality of Service (“QoS”),Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RadioAccess Network (“RAN”), Radio Access Technology (“RAT”), Random AccessProcedure (“RACH”), Random Access Response (“RAR”), Resource ElementGroup (“REG”), Radio Link Control (“RLC”), Radio Link Monitoring(“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal(“RS”), Remaining Minimum System Information (“RMSI”), Radio ResourceControl (“RRC”), Radio Resource Management (“RRM”), Resource SpreadMultiple Access (“RSMA”), Reference Signal Received Power (“RSRP”),Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access(“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”),Single Carrier Frequency Division Multiple Access (“SC-FDMA”), SecondaryCell (“SCell”), Shared Channel (“SCH”), Sub-carrier Spacing (“SCS”),Service Data Unit (“SDU”), System Information Block (“SIB”),SystemInformationBlockType1 (“SIB1”), SystemInformationBlockType2(“SIB2”), Subscriber Identity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Service LevelAgreement (“SLA”), Session Management Function (“SMF”), Special Cell(“SpCell”), Single Network Slice Selection Assistance Information(“S-NSSAI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”),Synchronization Signal Block (“SSB”), Supplementary Uplink (“SUL”),Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TAIndicator (“TAI”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), TimeDivision Orthogonal Cover Code (“TD-OCC”), Transmission Power Control(“TPC”), Transmission Reception Point (“TRP”), Transmission TimeInterval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”),Unified Data Management Function (“UDM”), Unified Data Repository(“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”), UniversalIntegrated Circuit Card (“UICC”), Uplink (“UL”), Universal MobileTelecommunications System (“UMTS”), User Plane (“UP”), Uplink Pilot TimeSlot (“UpPTS”), Ultra-reliability and Low-latency Communications(“URLLC”), UE Route Selection Policy (“URSP”), LTE Radio Interface(“Uu”), Vehicle-To-Everything (“V2X”), Visiting AMF (“vAMF”), VisitingNSSF (“vNSSF”), Visiting PLMN (“VPLMN”), Interconnecting Interface(“X2”) (“Xn”), and Worldwide Interoperability for Microwave Access(“WiMAX”).

In certain wireless communications networks, V2X communication may beused. In such networks, devices may not be compatible with one another.

BRIEF SUMMARY

Methods for V2X communication over multiple radio access types aredisclosed. Apparatuses and systems also perform the functions of theapparatus. One embodiment of a method includes establishing, via aremote unit, a first plurality of network connections for directcommunication with a mobile communication network and a second pluralityof network connections for direct vehicle-to-everything communicationwith other remote units over a plurality of radio access types. Incertain embodiments, the method includes receiving a request to transmita vehicle-to-everything communication. In various embodiments, themethod includes determining whether the vehicle-to-everythingcommunication is to be transmitted via a direct communication with amobile communication network or a direct vehicle-to-everythingcommunication with other remote units. In some embodiments, the methodincludes determining a radio access type of the plurality of radioaccess types for transmitting the vehicle-to-everything communicationvia a direct vehicle-to-everything communication. In certainembodiments, the method includes selecting a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type. In various embodiments, themethod includes requesting resources via the cell for transmitting thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication using the radio access type.

One apparatus for V2X communication over multiple radio access typesincludes a processor that: establishes a first plurality of networkconnections for direct communication with a mobile communication networkand a second plurality of network connections for directvehicle-to-everything communication with other remote units over aplurality of radio access types; receives a request to transmit avehicle-to-everything communication; determines whether thevehicle-to-everything communication is to be transmitted via a directcommunication with a mobile communication network or a directvehicle-to-everything communication with other remote units; determinesa radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; selects a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and requests resources via thecell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.

One method for V2X communication over multiple radio access typesincludes transmitting, from a remote unit, information indicating avehicle-to-everything capability of the remote unit. In variousembodiments, the method includes receiving a response to the informationindicating the vehicle-to-everything capability of the remote unit. Insuch embodiments, the response indicates whether the remote unit isauthorized to use the vehicle-to-everything capability.

One apparatus for V2X communication over multiple radio access typesincludes a transmitter that transmits information indicating avehicle-to-everything capability of the apparatus. In some embodiments,the apparatus includes a receiver that receives a response to theinformation indicating the vehicle-to-everything capability of theapparatus. In such embodiments, the response indicates whether theapparatus is authorized to use the vehicle-to-everything capability.

One method for V2X communication over multiple radio access typesincludes receiving information indicating a vehicle-to-everythingcapability of a remote unit. In various embodiments, the method includestransmitting a response to the information indicating thevehicle-to-everything capability of the remote unit. In suchembodiments, the response indicates whether the remote unit isauthorized to use the vehicle-to-everything capability.

One apparatus for V2X communication over multiple radio access typesincludes a receiver that receives information indicating avehicle-to-everything capability of a remote unit. In some embodiments,a transmitter that transmits a response to the information indicatingthe vehicle-to-everything capability of the remote unit. In suchembodiments, the response indicates whether the remote unit isauthorized to use the vehicle-to-everything capability.

One method for V2X communication over multiple radio access typesincludes configuring a remote unit with information indicating aplurality of mobile networks and a radio access type of a plurality ofradio access types for direct vehicle-to-everything communicationcorresponding to each mobile network of the plurality of mobilenetworks. In various embodiments, the method includes supporting aplurality of vehicle-to-everything applications. In such embodiments,each vehicle-to-everything application of the plurality ofvehicle-to-everything applications communicates via a directvehicle-to-everything communication using a corresponding radio accesstype of the plurality of radio access types.

One apparatus for V2X communication over multiple radio access typesincludes a processor that: configures the apparatus with informationindicating a plurality of mobile networks and a radio access type of aplurality of radio access types for direct vehicle-to-everythingcommunication corresponding to each mobile network of the plurality ofmobile networks; and supports a plurality of vehicle-to-everythingapplications, wherein each vehicle-to-everything application of theplurality of vehicle-to-everything applications communicates via adirect vehicle-to-everything communication using a corresponding radioaccess type of the plurality of radio access types.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for V2X communication over multiple radioaccess types;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for V2X communication over multiple radioaccess types;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for V2X communication over multiple radioaccess types;

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications including a registration procedure with V2Xauthorization;

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem for sending a PC5 message over multiple RATs in an autonomousmode;

FIG. 6 is a schematic block diagram illustrating one embodiment of asystem for sending a PC5 message over multiple RATs in a scheduled mode;

FIG. 7 is a flow chart diagram illustrating one embodiment of a methodfor a UE selecting a cell while the UE is camped in a 5G cell;

FIG. 8 is a flow chart diagram illustrating another embodiment of amethod for a UE selecting a cell while the UE is camped in a 5G cell;

FIG. 9 is a flow chart diagram illustrating one embodiment of a methodfor a UE selecting a cell while the UE is camped in a 4G cell;

FIG. 10 is a flow chart diagram illustrating one embodiment of a methodfor V2X communication over multiple radio access types;

FIG. 11 is a flow chart diagram illustrating another embodiment of amethod for V2X communication over multiple radio access types;

FIG. 12 is a flow chart diagram illustrating a further embodiment of amethod for V2X communication over multiple radio access types; and

FIG. 13 is a flow chart diagram illustrating yet another embodiment of amethod for V2X communication over multiple radio access types.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forV2X communication over multiple radio access types. In one embodiment,the wireless communication system 100 includes remote units 102 andnetwork units 104. Even though a specific number of remote units 102 andnetwork units 104 are depicted in FIG. 1, one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. The remote units 102 mayalso communicate directly with one or more of the other remote units102.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may establish a first plurality ofnetwork connections for direct communication with a mobile communicationnetwork and a second plurality of network connections for directvehicle-to-everything communication with other remote units 102 over aplurality of radio access types. In certain embodiments, the remote unit102 may receive a request to transmit a vehicle-to-everythingcommunication. In various embodiments, the remote unit 102 may determinewhether the vehicle-to-everything communication is to be transmitted viaa direct communication with a mobile communication network or a directvehicle-to-everything communication with other remote units 102. In someembodiments, the remote unit 102 may determine a radio access type ofthe plurality of radio access types for transmitting thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication. In certain embodiments, the remote unit 102 may select acell of a plurality of cells that supports vehicle-to-everythingresource management for the vehicle-to-everything communication via adirect vehicle-to-everything communication and the radio access type. Invarious embodiments, the remote unit 102 may request resources via thecell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.Accordingly, the remote unit 102 may be used for V2X communication overmultiple radio access types.

In various embodiments, a remote unit 102 may transmit informationindicating a vehicle-to-everything capability of the remote unit 102. Invarious embodiments, the remote unit 102 may receive a response to theinformation indicating the vehicle-to-everything capability of theremote unit 102. In such embodiments, the response indicates whether theremote unit 102 is authorized to use the vehicle-to-everythingcapability. Accordingly, the remote unit 102 may be used for V2Xcommunication over multiple radio access types.

In certain embodiments, a network unit 104 may receive informationindicating a vehicle-to-everything capability of a remote unit 102. Invarious embodiments, the network unit 104 may transmit a response to theinformation indicating the vehicle-to-everything capability of theremote unit 102. In such embodiments, the response indicates whether theremote unit 102 is authorized to use the vehicle-to-everythingcapability. Accordingly, the network unit 104 may be used for V2Xcommunication over multiple radio access types.

In one embodiment, a remote unit 102 may configure a remote unit withinformation indicating a plurality of mobile networks and a radio accesstype of a plurality of radio access types for directvehicle-to-everything communication corresponding to each mobile networkof the plurality of mobile networks. In various embodiments, the remoteunit 102 may support a plurality of vehicle-to-everything applications.In such embodiments, each vehicle-to-everything application of theplurality of vehicle-to-everything applications communicates via adirect vehicle-to-everything communication using a corresponding radioaccess type of the plurality of radio access types. Accordingly, theremote unit 102 may be used for V2X communication over multiple radioaccess types.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forV2X communication over multiple radio access types. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 may: establish a first pluralityof network connections for direct communication with a mobilecommunication network and a second plurality of network connections fordirect vehicle-to-everything communication with other remote units overa plurality of radio access types; receive a request to transmit avehicle-to-everything communication; determine whether thevehicle-to-everything communication is to be transmitted via a directcommunication with a mobile communication network or a directvehicle-to-everything communication with other remote units 102;determine a radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; select a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and request resources via thecell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.

In certain embodiments, the processor 202 may: configure the apparatus200 with information indicating a plurality of mobile networks and aradio access type of a plurality of radio access types for directvehicle-to-everything communication corresponding to each mobile networkof the plurality of mobile networks; and support a plurality ofvehicle-to-everything applications, wherein each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscommunicates via a direct vehicle-to-everything communication using acorresponding radio access type of the plurality of radio access types.The processor 202 is communicatively coupled to the memory 204, theinput device 206, the display 208, the transmitter 210, and the receiver212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Incertain embodiments, the transmitter 210 transmits informationindicating a vehicle-to-everything capability of the apparatus 200. Insome embodiments, the receiver 212 receives a response to theinformation indicating the vehicle-to-everything capability of theapparatus 200. In such embodiments, the response indicates whether theapparatus 200 is authorized to use the vehicle-to-everything capability.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forV2X communication over multiple radio access types. The apparatus 300includes one embodiment of the network unit 104. Furthermore, thenetwork unit 104 may include a processor 302, a memory 304, an inputdevice 306, a display 308, a transmitter 310, and a receiver 312. As maybe appreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In some embodiments, the receiver 312 receives information indicating avehicle-to-everything capability of a remote unit 102. In someembodiments, the transmitter 310 transmits a response to the informationindicating the vehicle-to-everything capability of the remote unit 102.In such embodiments, the response indicates whether the remote unit 102is authorized to use the vehicle-to-everything capability.

Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

In some embodiments, if a UE is to send a V2X message over a PC5interface, the UE may determine whether a cell supports certain carrierfrequencies for V2X communications. In such embodiments, if the celldoes not support the carrier frequencies the UE may have to search for acell that supports the carrier frequencies. The search may take intoaccount a list of PLMNs that the UE is enabled to use for PC5communications. In certain embodiments, a UE searching for a cell tosupport carrier frequencies for V2X communication may first look for thecell in its own PLMN and, if the UE is not successful, the UE may lookin cells of equivalent PLMNs until a cell is found that supports V2Xcommunications. In such embodiments, if the UE is outside coverage of3GPP specified RATs (e.g., LTE and NR cells are unavailable) on asidelink V2X frequency, then the UE may perform sidelink communicationin another manner, such as according to SL-V2X-Preconfiguration.

In various embodiments, a 5G capable UE may support both EPS V2Xcommunications (e.g., such as for safety services) and 5G V2X enhancedservices (e.g., such as for vehicle platooning). In some embodiments, if5G V2X capable UEs need to communicate with EPS V2X capable UEs, the UEsmay use E-UTRA over Uu to send a V2X communication over legacy PC5(e.g., E-UTRA).

As may be appreciated, a UE may have a number of services that require5G radio access technology and such services will not be available if a5G V2X capable UE uses E-UTRA and EPC due to communicating a V2X messageover E-UTRA PC5. As described herein, a UE may be able to determine abest cell to camp in to support V2X communications over PC5 over bothE-UTRA and NR without interrupting other V2X services. Furthermore, asdescribed herein a UE may identify how to transmit eV2X messages eitherbased on an enhanced E-UTRA radio or based on a NR radio.

In certain embodiments, during registration in an EPS, a UE may includein an initial attach request an indication that the UE is V2X capable.Moreover, an MME may check with an HSS to determine whether the UE isauthorized to use V2X services and may provide an indication to an eNBthat indicates whether the UE is authorized to use V2X. Based on thisindication the eNB may identify whether the UE is enabled to use ascheduled mode of operation in a cell.

In various embodiments, such as in 5G, a UE may support both E-UTRA PC5and NR PC5. Furthermore, in some embodiments, the UE may support aversion of E-UTRA that is enhanced (e.g., enhanced E-UTRA), such as withhigher data rates than standard E-UTRA. In certain embodiments, anNG-RAN node (e.g., eNB, gNB) may support scheduling resources for PC5messages sent via NR, E-UTRA, and/or an enhanced E-UTRA. Accordingly, anNG-RAN node may indicate whether a UE is authorized to use E-UTRA PC5and/or NR PC5 in a cell.

In some embodiments, a UE may use a single RAT and/or system (e.g., EPSor 5GS) over a Uu reference point (e.g., macro cell with a single RAT),and a RAN node may be able to configure the UE for multiple PC5 types ofcommunication (e.g., E-UTRA PC5 and/or NR PC5). As may be appreciated, aUE may use a dual connectivity feature (e.g., a secondary cell operatingin the same or in a different RAT than a master cell) together with PC5communication.

In various embodiments, a V2X capable UE may provide its V2Xcapabilities during an initial registration and/or mobility registrationprocedure with a 5GS. For example, a UE may include informationindicating that V2X is supported and/or the UE may provide an explicitindication of V2X services that the UE supports (e.g., safety V2Xservices using E-UTRA PC5, enhanced V2X services using NR PC5, etc.). Incertain embodiments, a registration request message may be authorized bya network function (e.g., UDM, PCF, AUSF, or another network function)that may determine (e.g., check) whether a UE is authorized to use V2Xservices and may provide an indication indicating whether the UE isauthorized to use PC5 communications over E-UTRA PC5 and/or NR PC5. Insuch embodiments, the network function may provide the indication to anAMF to indicate which PC5 types the UE is allowed to use. Moreover, theAMF may then provide information to an NG-RAN to indicate whether the UEis authorized to use V2X services over PC5 and may provide informationindicating the RATs supported.

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications 400 including a registration procedure with V2Xauthorization. The communications 400 include messages transmittedbetween a UE 402 (e.g., V2X UE), a RAN 404 (e.g., NG-RAN), an AMF 406,an AUSF 408, and a UDM 410. Each communication described herein mayinclude one or more messages.

In certain embodiments, in a first communication 412 transmitted fromthe UE 402 to the RAN 404, the UE 402 may transmit an initialregistration request that includes an indication that the UE 402 is V2Xcapable. In some embodiments, as part of the first communication 412,the UE 402 may include a generic indication (e.g., a single bit) or theUE 402 may be more explicit and indicate that the UE 402 supports basic(e.g., EPS based) and/or enhanced (e.g., 5G based) V2X capabilities.

In various embodiments, in a second communication 414 transmitted fromthe RAN 404 to the AMF 406, the RAN 404 may transmit information thatindicates AN parameters and/or information from the initial registrationrequest received by the RAN 404 from the UE 402.

In some embodiments, authentication and/or authorization messages 416may be transmitted between the UE 402, the RAN 404, the AMF 406, and/orthe AUSF 408 to perform authentication and/or authorization of the UE402.

In certain embodiments, UDM selection 418 is performed by the AMF 406.

In various embodiments, in a third communication 420 transmitted fromthe AMF 406 to the UDM 410, the AMF 406 may forward the V2X capabilityof the UE 402 to the UDM 410, such as within a Nudm_service requestmessage.

In some embodiments, in a fourth communication 422 transmitted from theUDM 410 to the AMF 406, the UDM 410, based on subscription information,may provide an indication to the AMF 406 that the UE 402 is authorizedto use E-UTRA PC5 and/or NR PC5. As part of the fourth communication422, the UDM 410 may also provide an indication that the UE 402 isenhanced E-UTRA capable. In certain embodiments, the AMF 406 may storeinformation about the authorization of the UE 402 to use E-UTRA PC5and/or NR PC5 in the UE's 402 MM context. In various embodiments, theAMF 406 may forward information about the authorization of the UE 402together with the UE's 402 MM context to other AMFs or MMEs. In someembodiments, the AMF 406 may process and/or store information about theauthorization of the UE 402 to facilitate signaling the informationwithin the UE 402 context (e.g., RAN 404) to the RAN 404 (e.g., NG-RANnode).

In certain embodiments, in a fifth communication 424 transmitted fromthe AMF 406 to the RAN 404, the AMF 406 may send the indication aboutthe authorization to use E-UTRA PC5 and/or NR PC5 to the RAN 404. Theindication may be within the UE's 402 RAN context encapsulated in amessage as part of various parameters. In various embodiments, the AMF406 may send the indication about the authorization to use E-UTRA PC5and/or NR PC5 during each transition from a CM-idle state to aCM-connected state.

In some embodiments, the RAN 404 stores 426 (e.g., in the UE 402context) information indicating whether the UE 402 is authorized tosupport EPS services, NR V2X services, E-UTRA PC5, and/or NR PC5.

In certain embodiments, in a sixth communication 428 transmitted fromthe RAN 404 to the UE 402, the RAN 404 may transmit a registrationaccept message to the UE 402.

As may be appreciated, while the communications 412 through 426 aredescribed for registration with a 5GS, similar communications may beused for registration with an EPS.

In various embodiments, after the UE 402 receives the sixthcommunication 428, the UE 402 may proceed to subscribe to V2X servicesfrom a V2X control function and/or may receive authorization to use PC5in a PLMN.

In some embodiments, authorization information may include the following(either provided by a V2X control function and/or preconfigured at theUE 402): 1) An authorization policy: authorization to perform PC5communication with a list of PLMNs for which the UE 402 is served by anE-UTRAN; and/or a list of geographical areas in which the UE 402 isauthorized to perform PC5 communications at times that the UE 402 is notserved by E-UTRA; 2) Radio configuration parameters at times duringwhich the UE 402 is not served by E-UTRAN: includes the radio parameterswith geographical areas and an indication of whether they are “operatormanaged” or “non-operator managed” (e.g., the UE 402 may use the radioparameters to perform V2X communications over PC5 reference point attimes in which the UE 402 is “not served by E-UTRAN” only if the UE 402can reliably locate itself in a corresponding geographical area,otherwise, the UE 402 is not authorized to transmit); 3) Policyparameters: mapping of destination layer 2 IDs (e.g., in a PC5 message)to V2X application IDs; mapping of per prose packet priority and packetdelay budget; and/or mapping of V2X application IDs to V2X frequencieswith geographical areas.

In certain embodiments, because a 5G UE 402 may support dual PC5capability (e.g., both E-UTRA PC5 and NR PC5 simultaneously), the UE 402may require configuration information to be aware of which PLMNs the UE402 is allowed to perform PC5 communications over E-UTRA or NR. Thisconfiguration information may be needed by the UE 402 if served by theRAN 404 and also if not served by the RAN 404. In various embodiments,the UE 402 may be configured with a list of PLMNs that the UE 402 isauthorized to perform PC5 communications over E-UTRA, enhanced E-UTRA,and/or NR. In some embodiments, if not served by the RAN 404, the UE 402may be configured with a list of geographical areas that the UE 402 isauthorized to perform PC5 communications over NR and/or E-UTRA.

In various embodiments, the UE 402 may be provided with informationindicating times during which a V2X application triggers to send amessage over PC5. In such embodiments, the UE 402 may need to identifyif V2X messages need to be sent over E-UTRA PC5, enhanced E-UTRA PC5, orNR PC5. Such embodiments may include configuring the UE 402 with amapping between V2X application IDs and PC5 RATs. In some embodiments, aV2X application ID may map to one or more PC5 RATs.

In some embodiments, a V2X application may indicate a priority of a V2Xmessage to a V2X layer in the UE 402. In such embodiments, based on thepriority requested, the UE 402 may determine whether the V2X messagewill be sent over E-UTRA or NR RAT based on priority requirements. Asmay be appreciated, information used to determine whether the V2Xmessage will be sent over E-UTRA or NR RAT may be configured at the UE402 (e.g., the UE 402 may be configured by a network with a mapping of apriority to a selected PC5 RAT (e.g., E-UTRA or NR).

As described herein, the UE 402 may include the following configurationparameters: a list of PLMNs in which the UE 402 is authorized to performE-UTRA, enhanced E-UTRA, and/or NR over PC5; a list of geographicalareas in which the UE 402 is authorized to perform E-UTRA, enhancedE-UTRA, and/or NR over PC5; a mapping of V2X application IDs to PC5RATs; and/or a mapping of a priority requested by a V2X application toone or more PC5 RATs. The configuration parameters may be configured inthe UE 402 using NAS protocol messages, using RRC protocol messages,and/or using other protocols carried over user plane IP protocols.

In certain embodiments, the UE 402 may be configured with authorizationto perform E-UTRA or NR and a gNB and/or eNB may decide dynamicallywhether enhanced E-UTRA may be used to transmit a V2X message. In oneexample, a cell may be configured with information that indicates thatfor a specific carrier frequency enhanced E-UTRA may be used. In such anexample, the cell may dynamically decide whether a V2X message can betransmitted using enhanced E-UTRA PC5. In such embodiments, this type ofconfiguration may be supported if a cell can detect that UEs in itsvicinity are enhanced E-UTRA PC5 capable (e.g., based on informationfrom the UDM 410).

In various embodiments, the UE 402 may be configured so that forspecific application IDs the UE 402 is E-UTRA PC5 authorized, and/orenhanced E-UTRA PC5 may be used in specific geographical locations. Insuch embodiments, if the UE 402 is triggered to transmit a V2X messagefor the specific application IDs, the UE 402 checks its geographicallocation to determine whether E-UTRA or enhanced E-UTRA is to be used.

In some embodiments, the UE 402 may be configured so that for a specificapplication ID, E-UTRA is authorized. In such embodiments, if the UE 402is enhanced E-UTRA capable and if the UE 402 starts a message exchange(e.g., for unicast communications), the UE 402 may indicate that it isenhanced E-UTRA capable and may decide to use enhanced E-UTRA to conveya PC5 message.

In certain embodiments, the RAN 404 may not be able to know and/orgather enough information for the UE's 402 transmission configurationfor a certain PC5 RAT. In such embodiments, the RAN 404 may know (e.g.,by network configuration) which other RAN node to query to learn the PC5configuration information. In some embodiments, a RAN node may broadcastor announce that it supports all types of PC5 communication. Moreover,some PC5 RATs may determine other RAN nodes' supported communicationswithout a query to the other RAN nodes and for other PC5 RATs the PC5RATs may need to query other RAN nodes to determine the other RAN nodes;supported communications. For example, a gNB may be able to configurethe UE 402 for NR PC5 transmission, but may not be able to determine theE-UTRA PC5 or enhance E-UTRA PC5 configuration by itself. However, thegNB may know which particular eNB to query to obtain such E-UTRA PC5 orenhance E-UTRA PC5 configuration. Moreover, the gNB may announce supportof E-UTRA PC5, enhance E-UTRA PC5, and NR PC5 communication.

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem 500 for sending a PC5 message over multiple RATs in an autonomousmode. The system 500 includes a UE 502. The UE 502 may be substantiallysimilar to the UE 402 and/or the remote unit 102 as described herein.Moreover, the UE 502 includes a V2X client 504 and has a V2Xconfiguration 506 (V2X config). The V2X configuration 506 may include anE-UTRA PC5 radio configuration, an NR PC5 radio configuration, a list ofapplication IDs for E-UTRA PC5, and/or a list of application IDS for NRPC5.

The UE 502 also includes a first V2X application 508 (first V2X app) anda second V2X application 510 (second V2X app). The UE 502 may beconfigured for E-UTRA PC5 512 and/or NR PC5 514. As illustrated, thesystem 500 also includes a V2X control function 516. In variousembodiments, the V2X control function 516 may transmit information 518indicating the V2X configuration 506.

In various embodiments, while the UE 502 is in an autonomous mode ofoperation, the UE 502 may determine a radio configuration for V2Xservices based on configuration policies of the V2X configuration 506.In one embodiment, the UE 502 determines the radio parameters to usebased on a geographical area. In some embodiments, if the radioconfiguration indicates both NR PC5 and E-UTRA PC5, the UE 502 uses bothradio parameters to listen for PC5 messages.

In certain embodiments, while the UE 502 is in an autonomous mode ofoperation and a V2X application requests to transmit a PC5 message, theUE 502 may determine whether the V2X message is to be sent over NR PC5or E-UTRA PC5 based on the configuration received from the V2X controlfunction 516. For example, while a V2X application may send a PC5message over a V2X layer the UE 502 may determine based on a V2Xapplication ID that the PC5 message must be sent over E-UTRA PC5 basedon radio configuration parameters.

FIG. 6 is a schematic block diagram illustrating one embodiment of asystem 600 for sending a PC5 message over multiple RATs in a scheduledmode. The system 600 includes the UE 502 and the V2X control function516 which are substantially the same as the UE 502 and the V2X controlfunction 516 of system 500. The system 600 also includes a first cell602 (e.g., cell 1, cell having a first PLMN ID−ID=1, cell supporting NRPC5 radio frequencies), a second cell 604 (e.g., cell 2, cell having aPLMN ID−ID=1, cell supporting E-UTRA PC5 radio frequencies), and a thirdcell 606 (e.g., cell 3, cell having a second PLMN ID=ID=2, cellsupporting NR PC5 and E-UTRA PC5 radio frequencies).

In some embodiments, the UE 502 may be camped out on the first cell 602.Moreover, in various embodiments, the V2X control function 516 maytransmit information 610 indicating the V2X configuration 506. In oneembodiment, the V2X configuration 506 may indicate that the first V2Xapplication 508 has an ID=1 and that the first V2X application 508 isconfigured for NR PC5. Moreover, in such an embodiment, the V2Xconfiguration 506 may indicate that the second V2X application 510 hasan ID=2 and that the second V2X application 510 is configured for E-UTRAPC5. In certain embodiments, the UE 502 may determine that the secondV2X application 510 requires E-UTRA PC5 and the UE 502 may be aware thatthe first V2X application 508 requires NR PC5. The first cell 602 maynot support E-UTRA PC5 so the UE 502 may search for a cell supportingE-UTRA PC5. The second cell 604 may support E-UTRA PC5, but only E-UTRAPC5 is supported over Uu while the third cell 606 supports E-UTRA PC5and NR PC5 over Uu. Accordingly, the UE 502 may select 612 the thirdcell 606 to transmit a V2X message of the second V2X application 510because the third cell 606 also supports PC5 communications for thefirst V2X application 508.

In various embodiments, while in a scheduled mode of operation, if theUE 502 intends to use radio resources for V2X communication over PC5 theUE 502 may act as described in one or more of the following embodiments.

In certain embodiments, if the UE 502 is in an RRC IDLE state: if a V2Xapplication triggers the V2X layer to send a PC5 message over PC5, theUE 502 determines based on a V2X app ID to PC5 RAT whether the PC5message is sent over E-UTRA or NR; the UE 502 then checks whether theserving cell has the radio resources available to support E-UTRA and/orNR PC5 (e.g., by checking the SIB information); if performing a cellsearch the UE 502 checks whether there are existing V2X communicationsthat require NR and/or E-UTRA over PC5. For example, if there areexisting applications that use NR and E-UTRA PC5, the UE 502 may searchfor a cell that supports both. If only E-UTRA PC5 is active, then the UE502 may give priority to an E-UTRA cell. If only NR PC5 is active, thenthe UE 502 may give priority to an NR cell, and so forth.

In some embodiments, if a cell supports requested radio resources, theUE 502 may enter an RRC_CONNECTED state and request resource allocationto send a PC5 message. In various embodiments, if a cell does notsupport requested radio resources, the UE 502 may search for a cell inan existing PLMN that is operating the requested (e.g., provisioned)radio resources.

In certain embodiments, if the UE 502 does not find a cell in aregistered PLMN, the UE 502 may check a cell in an equivalent PLMN inwhich authorization for V2X communications over a PC5 reference point isallowed. In some embodiments, if the UE 502 finds a cell in whichauthorization for V2X communications over a PC5 reference point isallowed but the UE 502 is not in the registered PLMN or a PLMNequivalent to the registered PLMN, and that cell belongs to a PLMNauthorized for V2X communications over PC5 reference point and providesradio resources for V2X service, then the UE 502 may perform PLMNselection triggered by V2X communications over PC5 reference point asdefined in TS 23.122.

In various embodiments, if the UE 502 finds a cell in whichauthorization for V2X communications over a PC5 reference point isallowed but the cell is not in a PLMN authorized for V2X communicationsover the PC5 reference point, the UE 502 may not use V2X communicationsover the PC5 reference point.

In certain embodiments, if the UE 502 does not find any suitable cell inany PLMN, then the UE 502 may consider itself not served by NG-RAN anduse radio resources provisioned in a UE or a UICC. If no such provisionexists in the ME or the UICC or the provision does not authorize V2Xcommunications over a PC5 reference point, then the UE 502 is notauthorized to transmit.

In some embodiments, the UE 502 may have existing V2X sessions active anover PC5 (e.g., NR PC5) and a V2X application ID may require to send aPC5 message over another PC5 interface (e.g., over E-UTRA PC5), butthere may be no cell in the vicinity that supports both NR PC5 andE-UTRA PC5. In such embodiments, the UE 502 may have to drop theexisting NR PC5 sessions in order to attach to a cell supporting E-UTRAPC5. However, if there are NR PC5 services that require constantcommunication, dropping the existing NR PC5 sessions may interrupt suchservices. Accordingly, the UE 502 may determine whether a V2X service isallowed to preempt other services.

In various embodiments, the UE 502 may receive configuration informationwith a list of V2X application IDs that may be preempted if a new V2Xapplication requires a service that is not supported by the serving celland/or PLMN. The list may also include information with V2X applicationIDs for which preemption is not allowed. In such embodiments, if a V2Xapplication ID requests to send a PC5 message that is not supported in acurrent cell, the UE 502 may check whether the existing V2X applicationcan be preempted.

In certain embodiments, a V2X application may indicate that a PC5message is for an emergency (e.g., a car broadcasting an emergencybraking alert). In such embodiments, the UE 502 may immediately preemptall other V2X services and search for a cell that supports a carrierfrequency for the emergency. In one embodiment, the UE 502 may beconfigured with a specific V2X application ID that is mapped to anemergency PC5 message.

In some embodiments, the UE 502 may request a RAN node for a differentPC5 RAT and a network (e.g., the RAN node and/or a core network) mayinitiate either idle mode mobility (e.g., RRC release with a redirectionindication) or connected mode mobility to a RAN node that supports a PC5RAT requested. For this purpose, the RAN node, at a location on whichthe UE 502 is currently camping, may announce to the UE 502 thatmultiple types of PC5 RATs are supported even though that RAN node willnot support all PC5 RATs. In such embodiments, the RAN node may notsupport all the PC5 RAT types but may be configured with other RAN nodesin the vicinity of this node that support the requested PC5 RAT. Such anetwork-based solution may be referred to as a fallback for V2Xservice(s) over PC5 interface.

In various embodiments, if the UE 502 is in an RRC IDLE mode, the UE 502may request resources for PC5 transmission from a RAN by entering anRRC_CONNECTED state. In certain embodiments, if the RAN node does notsupport a requested PC5 RAT, the RAN node may send an RRC releasemessage including a redirect indication that contains a list of targetcells that support the requested PC5 RAT. In such embodiments, the UE502 may carry an idle mode mobility procedure to attach to a new celland request resources for PC5 transmission.

In certain embodiments, if the UE 502 is in an ECM and/or RRC CONNECTEDmode, a RAN node may initiate a handover by sending a handover requesttowards an MME and/or an AMF. In some embodiments, in a handoverrequest, a RAN node may include an indication for a PC5 RAT requested.In various embodiments, an MME and/or an AMF may identify a target RANnode that supports requested PC5 and may initiate a handover commandtowards a RAN node that supports the requested PC5 RAT. In certainembodiments, a source RAN node may include, in a handover requiredmessage, a target cell ID that supports a requested PC5 RAT.

In some embodiments, if the UE 502 is in an RRC_CONNECTED mode and asource RAN node is configured target RAN nodes supporting certain PC5RATs, the source RAN node may initiate a handover by sending a handoverrequest towards a target RAN node (e.g., via an X2 or an Xn interface).

As may be appreciated, V2X applications may tolerate a small delaybefore a radio transmission is possible (e.g., 20-50 ms delay). Such adelay may result from a mobility procedure (e.g., idle mode or connectedmode mobility). In certain embodiments, a RAN node may announce to theUE 502 which of supported PC5 RATs are associated with a certain smalldelay. In such embodiments, the UE 502 may be able to assess whether anapplication request for transmission over a different PC5 RAT 1) has ahigher priority (e.g., to pre-empt current PC5 RAT) and/or 2) theapplication can tolerate a certain small delay for cell change. In someembodiments, an autonomous (e.g., UE-based) change of cell performed bythe UE 502 may have a larger delay than a network-based solution becausethe UE 502 may need to scan and tune to cells supporting a different PC5RAT.

FIG. 7 is a flow chart diagram illustrating one embodiment of a method700 for a UE selecting a cell while the UE is camped in a 5G cell. Themethod 700 includes a UE camped 702 on a 5G cell. The method 700includes determining 704 whether a V2X application or an eV2Xapplication is triggered. If an eV2X application is triggered, themethod 700 may determine 706 whether the 5G cell provides resources foreV2X communication. If the 5G cell provides resources for eV2Xcommunication, the method 700 may perform 708 5G eV2X TX-RX. If the 5Gcell does not provide resources for eV2X communication, the method 700may determine 710 whether there are other 5G frequencies available forsupporting eV2X. If there are other 5G frequencies available, 5G eV2XTX-RX may be performed on another 5G frequency.

If a V2X application is triggered, the method 700 may determine 712whether the 5G cell provides resources for V2X communication over 4Gresources. If the 5G cell provides resources for V2X communication over4G resources, the method 700 may perform 714 4G V2X TX-RX. If the 5Gcell does not provide resources for V2X communication over 4G resources,the method 700 may determine 716 whether other 5G frequencies supportingV2X communications are available. If other 5G frequencies supporting V2Xcommunications are available, the method 700 may reselect 718 another 5Gfrequency and the method 700 may return to determining 712 whether the5G cell provides resources for V2X communication over 4G resources. Ifother 5G frequencies supporting V2X communications are not available,the method 700 may search 720 for a 4G cell that supports V2X, and themethod 700 may end.

FIG. 8 is a flow chart diagram illustrating another embodiment of amethod 800 for a UE selecting a cell while the UE is camped in a 5Gcell. The method 800 includes a UE camped 802 on a 5G cell. The method800 includes determining 804 whether a V2X application or an eV2Xapplication is triggered. If an eV2X application is triggered, themethod 800 may determine 806 whether the 5G cell provides resources foreV2X communication. If the 5G cell provides resources for eV2Xcommunication, the method 800 may perform 808 5G eV2X TX-RX. If the 5Gcell does not provide resources for eV2X communication, the method 800may determine 810 whether there are other 5G frequencies available forsupporting eV2X.

If there are other 5G frequencies available for supporting eV2X, themethod 800 may determine 812 whether the UE runs other V2X services. Ifthe UE does not run other V2X services, the method 800 may perform 814V2X transmission over a new cell. If the UE does run other V2X services,the method 800 may determine 816 whether the other V2X services aresupported at a new cell. If the other V2X services are supported at thenew cell, the method 800 may perform 814 V2X transmission over the newcell. If the other V2X services are not supported at the new cell, themethod 800 may determine 818 whether the other V2X services can bepreempted. If the other V2X services can be preempted, the method 800may perform 814 V2X transmission over the new cell. If the other V2Xservices cannot be preempted, the method 800 may search 820 for a newcell and return to determining 810 whether there are other 5Gfrequencies available for supporting eV2X.

If a V2X application is triggered, the method 800 may determine 822whether the 5G cell provides resources for V2X communication over 4Gresources. If the 5G cell provides resources for V2X communication over4G resources, the method 800 may determine 812 whether the UE runs otherV2X services. The method 800 may then proceed through steps 812 through820 as discussed herein. If the method 800 searches 820 for a new cell,the method 800 may end.

If the 5G cell does not provide resources for V2X communication over 4Gresources, the method 800 may determine 824 whether other 5G frequenciessupporting V2X communications are available. If other 5G frequenciessupporting V2X communications are available, the method 800 may reselect826 another 5G frequency and the method 800 may return to determining822 whether the 5G cell provides resources for V2X communication over 4Gresources. If other 5G frequencies supporting V2X communications are notavailable, the method 800 may search 828 for a 4G cell that supportsV2X, and the method 800 may end.

FIG. 9 is a flow chart diagram illustrating one embodiment of a method900 for a UE selecting a cell while the UE is camped in a 4G cell. Themethod 900 includes a UE camped 902 on a 4G cell. The method 900includes determining 904 whether a V2X application or an eV2Xapplication is triggered. If an eV2X application is triggered, themethod 900 may determine 906 whether the 4G cell supports eV2Xfrequencies. If the 4G cell does not support eV2X frequencies, themethod 900 may search 908 for a new cell. If the 4G cell does supportV2X frequencies, the method 900 may determine 910 whether the UE hasother V2X services. If the UE has other V2X services, the method 900 maydetermine 912 whether the other V2X services are supported at a newcell. If the other V2X services are supported at the new cell, themethod 900 may perform 914 eV2X TX-RX. If the other V2X services are notsupported at the new cell, the method 900 may determine 916 whether theother V2X services can be preempted. If the other V2X services can bepreempted, the method 800 may perform 914 eV2X TX-RX. If the other V2Xservices cannot be preempted, the method 900 may search 908 for a newcell.

If a V2X application is triggered, the method 900 may determine 918whether the 4G cell provides resources for V2X communication over 4Gresources. If the 4G cell provides resources for V2X communication over4G resources, the method 900 may perform 920 V2X TX-RX. If the 4G celldoes not provide resources for V2X communication over 4G resources, themethod 900 may determine 922 whether other 4G frequencies supporting V2Xcommunications are available. If other 4G frequencies supporting V2Xcommunications are available, the method 900 may reselect 924 another 4Gfrequency and the method 900 may return to determining 918 whether the4G cell provides resources for V2X communication over 4G resources. Ifother 4G frequencies supporting V2X communications are not available,the method 900 may search 926 for a 4G cell that supports V2X, and themethod 900 may end.

FIG. 10 is a flow chart diagram illustrating one embodiment of a method1000 for V2X communication over multiple radio access types. In someembodiments, the method 1000 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1000 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1000 may include establishing 1002, via a remote unit 102, afirst plurality of network connections for direct communication with amobile communication network and a second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a plurality of radio access types. In certainembodiments, the method 1000 includes receiving 1004 a request totransmit a vehicle-to-everything communication. In various embodiments,the method 1000 includes determining 1006 whether thevehicle-to-everything communication is to be transmitted via a directcommunication with a mobile communication network or a directvehicle-to-everything communication with other remote units 102. In someembodiments, the method 1000 includes determining 1008 a radio accesstype of the plurality of radio access types for transmitting thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication. In certain embodiments, the method 1000 includesselecting 1010 a cell of a plurality of cells that supportsvehicle-to-everything resource management for the vehicle-to-everythingcommunication via a direct vehicle-to-everything communication and theradio access type. In various embodiments, the method 1000 includesrequesting 1012 resources via the cell for transmitting thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication using the radio access type.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, new radio, or a combinationthereof. In some embodiments, the method 1000 further comprisessupporting a plurality of vehicle-to-everything applications, whereineach vehicle-to-everything application of the plurality ofvehicle-to-everything applications uses a corresponding networkconnection of the second plurality of network connections for directvehicle-to-everything communication with other remote units 102 over acorresponding radio access type of the plurality of radio access types.

In various embodiments, each vehicle-to-everything application of theplurality of vehicle-to-everything applications has avehicle-to-everything application identifier. In one embodiment, themethod 1000 further comprises determining the radio access type fortransmitting a vehicle-to-everything communication via directvehicle-to-everything communication based on a mapping of thevehicle-to-everything application identifier corresponding to avehicle-to-everything application of the plurality ofvehicle-to-everything applications to a specific radio access type.

In certain embodiments, the method 1000 further comprises determiningthe preemption of a first vehicle-to-everything application of theplurality of vehicle-to-everything applications based on a mapping ofthe vehicle-to-everything application identifier corresponding to thefirst vehicle-to-everything application to a preemption flag. In someembodiments, the method 1000 further comprises determining the cell thatsupports vehicle-to-everything resource management based on avehicle-to-everything carrier frequency of the firstvehicle-to-everything application of the plurality ofvehicle-to-everything applications.

In various embodiments, the method 1000 further comprises determiningwhether the cell supports vehicle-to-everything resource managementbased on a vehicle-to-everything carrier frequency of a secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications. In one embodiment, the method 1000further comprises determining that a second vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscannot be preempted and, in response to the cell not supportingvehicle-to-everything resource management based on thevehicle-to-everything carrier frequency of the secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications, selecting a different cell of theplurality of cells that supports vehicle-to-everything resourcemanagement and the carrier frequency of the second vehicle-to-everythingapplication.

FIG. 11 is a flow chart diagram illustrating another embodiment of amethod 1100 for V2X communication over multiple radio access types. Insome embodiments, the method 1100 is performed by an apparatus, such asthe remote unit 102. In certain embodiments, the method 1100 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1100 may include transmitting 1102, from a remote unit 102,information indicating a vehicle-to-everything capability of the remoteunit 102. In various embodiments, the method 1100 includes receiving1104 a response to the information indicating the vehicle-to-everythingcapability of the remote unit 102. In such embodiments, the responseindicates whether the remote unit 102 is authorized to use thevehicle-to-everything capability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the remote unit 102 is transmittedduring a registration procedure. In some embodiments, the informationindicating the vehicle-to-everything capability of the remote unit 102indicates whether vehicle-to-everything communication is supported. Invarious embodiments, the information indicating thevehicle-to-everything capability of the remote unit 102 indicates whichvehicle-to-everything services are supported by the remote unit 102, andthe vehicle-to-everything services comprise evolved universalterrestrial radio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remoteunit 102 to use the vehicle-to-everything capability. In someembodiments, the unified data management indicates to an access andmobility management function which radio access types that the remoteunit 102 is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access and new radio. In one embodiment, theaccess and mobility management function indicates to a radio accessnetwork authorization to carry out resource management for directvehicle-to-everything communication for the remote unit 102 for a newradio access type, an evolved universal terrestrial radio access type,or a combination thereof.

FIG. 12 is a flow chart diagram illustrating a further embodiment of amethod 1200 for V2X communication over multiple radio access types. Insome embodiments, the method 1200 is performed by an apparatus, such asthe network unit 104. In certain embodiments, the method 1200 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1200 may include receiving 1202 information indicating avehicle-to-everything capability of a remote unit 102. In variousembodiments, the method 1200 includes transmitting 1204 a response tothe information indicating the vehicle-to-everything capability of theremote unit 102. In such embodiments, the response indicates whether theremote unit 102 is authorized to use the vehicle-to-everythingcapability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the remote unit 102 is transmittedduring a registration procedure. In some embodiments, the informationindicating the vehicle-to-everything capability of the remote unit 102indicates whether vehicle-to-everything communication is supported. Invarious embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whichvehicle-to-everything services are supported by the remote unit 102, andthe vehicle-to-everything services comprise evolved universalterrestrial radio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remoteunit 102 to use the vehicle-to-everything capability. In someembodiments, the unified data management indicates to an access andmobility management function which radio access types that the remoteunit 102 is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access and new radio. In one embodiment, theaccess and mobility management function indicates to a radio accessnetwork authorization to carry out resource management for directvehicle-to-everything communication for the remote unit 102 for a newradio access type, an evolved universal terrestrial radio access type,or a combination thereof.

FIG. 13 is a flow chart diagram illustrating yet another embodiment of amethod 1300 for V2X communication over multiple radio access types. Insome embodiments, the method 1300 is performed by an apparatus, such asthe remote unit 102. In certain embodiments, the method 1300 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 1300 may include configuring 1302 a remote unit 102 withinformation indicating a plurality of mobile networks and a radio accesstype of a plurality of radio access types for directvehicle-to-everything communication corresponding to each mobile networkof the plurality of mobile networks. In various embodiments, the method1300 includes supporting 1304 a plurality of vehicle-to-everythingapplications. In such embodiments, each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscommunicates via a direct vehicle-to-everything communication using acorresponding radio access type of the plurality of radio access types.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, enhanced evolved universalterrestrial radio access, new radio, or some combination thereof. Insome embodiments, the method 1300 further comprises configuring theremote unit 102 with information indicating geographic areas forcommunication, wherein each geographic area of the geographic areas hasa corresponding radio access type of the plurality of radio accesstypes. In various embodiments, the method 1300 further comprisesreceiving a trigger, from a vehicle-to-everything application of theplurality of vehicle-to-everything applications, to send a message via avehicle-to-everything communication.

In one embodiment, the method 1300 further comprises selecting to send amessage via a direct vehicle-to-everything communication and determininga radio access type of the plurality of radio access types fortransmitting the message via the direct vehicle-to-everythingcommunication. In certain embodiments, in an autonomous mode, the remoteunit 102 determines the message radio access type based on configurationinformation received from a vehicle-to-everything control function. Insome embodiments, the message comprises a priority.

In various embodiments, the method 1300 further comprises determining atransmission radio access type of the plurality of radio access typesfor transmitting the message based on the priority. In one embodiment,the method 1300 further comprises configuring the remote unit 102 with amapping between the priority and at least one radio access type of theplurality of radio access types. In certain embodiments, thetransmission radio access type of the plurality of radio access typesfor transmitting the message is determined based on the mapping.

In some embodiments, the method 1300 further comprises configuring theremote unit 102 with a mapping between application identifierscorresponding to the plurality of vehicle-to-everything applications andat least one radio access type of the plurality of radio access types.

In one embodiment, a method comprises: establishing, via a remote unit,a first plurality of network connections for direct communication with amobile communication network and a second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a plurality of radio access types; receiving a requestto transmit a vehicle-to-everything communication; determining whetherthe vehicle-to-everything communication is to be transmitted via adirect communication with a mobile communication network or a directvehicle-to-everything communication with other remote units; determininga radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; selecting a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and requesting resources viathe cell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, new radio, or a combinationthereof.

In some embodiments, the method further comprises supporting a pluralityof vehicle-to-everything applications, wherein eachvehicle-to-everything application of the plurality ofvehicle-to-everything applications uses a corresponding networkconnection of the second plurality of network connections for directvehicle-to-everything communication with other remote units over acorresponding radio access type of the plurality of radio access types.

In various embodiments, each vehicle-to-everything application of theplurality of vehicle-to-everything applications has avehicle-to-everything application identifier.

In one embodiment, the method further comprises determining the radioaccess type for transmitting a vehicle-to-everything communication viadirect vehicle-to-everything communication based on a mapping of thevehicle-to-everything application identifier corresponding to avehicle-to-everything application of the plurality ofvehicle-to-everything applications to a specific radio access type.

In certain embodiments, the method further comprises determining thepreemption of a first vehicle-to-everything application of the pluralityof vehicle-to-everything applications based on a mapping of thevehicle-to-everything application identifier corresponding to the firstvehicle-to-everything application to a preemption flag.

In some embodiments, the method further comprises determining the cellthat supports vehicle-to-everything resource management based on avehicle-to-everything carrier frequency of the firstvehicle-to-everything application of the plurality ofvehicle-to-everything applications.

In various embodiments, the method further comprises determining whetherthe cell supports vehicle-to-everything resource management based on avehicle-to-everything carrier frequency of a secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications.

In one embodiment, the method further comprises determining that asecond vehicle-to-everything application of the plurality ofvehicle-to-everything applications cannot be preempted and, in responseto the cell not supporting vehicle-to-everything resource managementbased on the vehicle-to-everything carrier frequency of the secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications, selecting a different cell of theplurality of cells that supports vehicle-to-everything resourcemanagement and the carrier frequency of the second vehicle-to-everythingapplication.

In one embodiment, an apparatus comprises: a processor that: establishesa first plurality of network connections for direct communication with amobile communication network and a second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a plurality of radio access types; receives a requestto transmit a vehicle-to-everything communication; determines whetherthe vehicle-to-everything communication is to be transmitted via adirect communication with a mobile communication network or a directvehicle-to-everything communication with other remote units; determinesa radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; selects a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and requests resources via thecell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, new radio, or a combinationthereof.

In some embodiments, the processor supports a plurality ofvehicle-to-everything applications, and each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications usesa corresponding network connection of the second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a corresponding radio access type of the plurality ofradio access types.

In various embodiments, each vehicle-to-everything application of theplurality of vehicle-to-everything applications has avehicle-to-everything application identifier.

In one embodiment, the processor determines the radio access type fortransmitting a vehicle-to-everything communication via directvehicle-to-everything communication based on a mapping of thevehicle-to-everything application identifier corresponding to avehicle-to-everything application of the plurality ofvehicle-to-everything applications to a specific radio access type.

In certain embodiments, the processor determines the preemption of afirst vehicle-to-everything application of the plurality ofvehicle-to-everything applications based on a mapping of thevehicle-to-everything application identifier corresponding to the firstvehicle-to-everything application to a preemption flag.

In some embodiments, the processor determines the cell that supportsvehicle-to-everything resource management based on avehicle-to-everything carrier frequency of the firstvehicle-to-everything application of the plurality ofvehicle-to-everything applications.

In various embodiments, the processor determines whether the cellsupports vehicle-to-everything resource management based on avehicle-to-everything carrier frequency of a secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications.

In one embodiment, the processor determines that a secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications cannot be preempted and, in responseto the cell not supporting vehicle-to-everything resource managementbased on the vehicle-to-everything carrier frequency of the secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications, selects a different cell of theplurality of cells that supports vehicle-to-everything resourcemanagement and the carrier frequency of the second vehicle-to-everythingapplication.

In one embodiment, a method comprises: transmitting, from a remote unit,information indicating a vehicle-to-everything capability of the remoteunit; and receiving a response to the information indicating thevehicle-to-everything capability of the remote unit, wherein theresponse indicates whether the remote unit is authorized to use thevehicle-to-everything capability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the remote unit is transmittedduring a registration procedure.

In some embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whethervehicle-to-everything communication is supported.

In various embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whichvehicle-to-everything services are supported by the remote unit, and thevehicle-to-everything services comprise evolved universal terrestrialradio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remoteunit to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an accessand mobility management function which radio access types that theremote unit is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access, new radio, or a combination thereof.

In one embodiment, the access and mobility management function indicatesto a radio access network authorization to carry out resource managementfor direct vehicle-to-everything communication for the remote unit for anew radio access type, an evolved universal terrestrial radio accesstype, or a combination thereof.

In one embodiment, an apparatus comprises: a transmitter that transmitsinformation indicating a vehicle-to-everything capability of theapparatus; and a receiver that receives a response to the informationindicating the vehicle-to-everything capability of the apparatus,wherein the response indicates whether the apparatus is authorized touse the vehicle-to-everything capability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the apparatus is transmitted duringa registration procedure.

In some embodiments, the information indicating thevehicle-to-everything capability of the apparatus indicates whethervehicle-to-everything communication is supported.

In various embodiments, the information indicating thevehicle-to-everything capability of the apparatus indicates whichvehicle-to-everything services are supported by the apparatus, and thevehicle-to-everything services comprise evolved universal terrestrialradio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes theapparatus to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an accessand mobility management function which radio access types that theapparatus is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access, new radio, or a combination thereof.

In one embodiment, the access and mobility management function indicatesto a radio access network authorization to carry out resource managementfor direct vehicle-to-everything communication for the apparatus for anew radio access type, an evolved universal terrestrial radio accesstype, or a combination thereof.

In one embodiment, a method comprises: receiving information indicatinga vehicle-to-everything capability of a remote unit; and transmitting aresponse to the information indicating the vehicle-to-everythingcapability of the remote unit, wherein the response indicates whetherthe remote unit is authorized to use the vehicle-to-everythingcapability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the remote unit is transmittedduring a registration procedure.

In some embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whethervehicle-to-everything communication is supported.

In various embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whichvehicle-to-everything services are supported by the remote unit, and thevehicle-to-everything services comprise evolved universal terrestrialradio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remoteunit to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an accessand mobility management function which radio access types that theremote unit is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access, new radio, or a combination thereof.

In one embodiment, the access and mobility management function indicatesto a radio access network authorization to carry out resource managementfor direct vehicle-to-everything communication for the remote unit for anew radio access type, an evolved universal terrestrial radio accesstype, or a combination thereof.

In one embodiment, an apparatus comprises: a receiver that receivesinformation indicating a vehicle-to-everything capability of a remoteunit; and a transmitter that transmits a response to the informationindicating the vehicle-to-everything capability of the remote unit,wherein the response indicates whether the remote unit is authorized touse the vehicle-to-everything capability.

In certain embodiments, the information indicating thevehicle-to-everything capability of the remote unit is transmittedduring a registration procedure.

In some embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whethervehicle-to-everything communication is supported.

In various embodiments, the information indicating thevehicle-to-everything capability of the remote unit indicates whichvehicle-to-everything services are supported by the remote unit, and thevehicle-to-everything services comprise evolved universal terrestrialradio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remoteunit to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an accessand mobility management function which radio access types that theremote unit is enabled to use.

In various embodiments, the radio access types comprise evolveduniversal terrestrial radio access, new radio, or a combination thereof.

In one embodiment, the access and mobility management function indicatesto a radio access network authorization to carry out resource managementfor direct vehicle-to-everything communication for the remote unit for anew radio access type, an evolved universal terrestrial radio accesstype, or a combination thereof.

In one embodiment, a method comprises: configuring a remote unit withinformation indicating a plurality of mobile networks and a radio accesstype of a plurality of radio access types for directvehicle-to-everything communication corresponding to each mobile networkof the plurality of mobile networks; and supporting a plurality ofvehicle-to-everything applications, wherein each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscommunicates via a direct vehicle-to-everything communication using acorresponding radio access type of the plurality of radio access types.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, enhanced evolved universalterrestrial radio access, new radio, or some combination thereof.

In some embodiments, the method further comprises configuring the remoteunit with information indicating geographic areas for communication,wherein each geographic area of the geographic areas has a correspondingradio access type of the plurality of radio access types.

In various embodiments, the method further comprises receiving atrigger, from a vehicle-to-everything application of the plurality ofvehicle-to-everything applications, to send a message via avehicle-to-everything communication.

In one embodiment, the method further comprises selecting to send amessage via a direct vehicle-to-everything communication and determininga radio access type of the plurality of radio access types fortransmitting the message via the direct vehicle-to-everythingcommunication.

In certain embodiments, in an autonomous mode, the remote unitdetermines the message radio access type based on configurationinformation received from a vehicle-to-everything control function.

In some embodiments, the message comprises a priority.

In various embodiments, the method further comprises determining atransmission radio access type of the plurality of radio access typesfor transmitting the message based on the priority.

In one embodiment, the method further comprises configuring the remoteunit with a mapping between the priority and at least one radio accesstype of the plurality of radio access types.

In certain embodiments, the transmission radio access type of theplurality of radio access types for transmitting the message isdetermined based on the mapping.

In some embodiments, the method further comprises configuring the remoteunit with a mapping between application identifiers corresponding to theplurality of vehicle-to-everything applications and at least one radioaccess type of the plurality of radio access types.

In one embodiment, an apparatus comprises: a processor that: configuresthe apparatus with information indicating a plurality of mobile networksand a radio access type of a plurality of radio access types for directvehicle-to-everything communication corresponding to each mobile networkof the plurality of mobile networks; and supports a plurality ofvehicle-to-everything applications, wherein each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscommunicates via a direct vehicle-to-everything communication using acorresponding radio access type of the plurality of radio access types.

In certain embodiments, the plurality of radio access types comprisesevolved universal terrestrial radio access, enhanced evolved universalterrestrial radio access, new radio, or some combination thereof.

In some embodiments, the processor configures the apparatus withinformation indicating geographic areas for communication, and eachgeographic area of the geographic areas has a corresponding radio accesstype of the plurality of radio access types.

In various embodiments, the apparatus further comprises a receiver thatreceives a trigger, from a vehicle-to-everything application of theplurality of vehicle-to-everything applications, to send a message via avehicle-to-everything communication.

In one embodiment, the processor selects to send a message via a directvehicle-to-everything communication and determines a radio access typeof the plurality of radio access types for transmitting the message viathe direct vehicle-to-everything communication.

In certain embodiments, in an autonomous mode, the processor determinesthe message radio access type based on configuration informationreceived from a vehicle-to-everything control function.

In some embodiments, the message comprises a priority.

In various embodiments, the processor determines a transmission radioaccess type of the plurality of radio access types for transmitting themessage based on the priority.

In one embodiment, the processor configures the apparatus with a mappingbetween the priority and at least one radio access type of the pluralityof radio access types.

In certain embodiments, the transmission radio access type of theplurality of radio access types for transmitting the message isdetermined based on the mapping.

In some embodiments, the processor configures the apparatus with amapping between application identifiers corresponding to the pluralityof vehicle-to-everything applications and at least one radio access typeof the plurality of radio access types.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. A method comprising: establishing, via aremote unit comprising dual connectivity capability, a first pluralityof network connections for direct communication with a mobilecommunication network and a second plurality of concurrent networkconnections for direct vehicle-to-everything communication with otherremote units over a plurality of radio access types, wherein theplurality of radio access types comprises evolved universal terrestrialradio access and new radio; receiving a request to transmit avehicle-to-everything communication; determining whether thevehicle-to-everything communication is to be transmitted via a directcommunication with a mobile communication network or a directvehicle-to-everything communication with other remote units; determininga radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; selecting a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and requesting resources viathe cell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.2. The method of claim 1, further comprising supporting a plurality ofvehicle-to-everything applications, wherein each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications usesa corresponding network connection of the second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a corresponding radio access type of the plurality ofradio access types.
 3. The method of claim 2, wherein eachvehicle-to-everything application of the plurality ofvehicle-to-everything applications has a vehicle-to-everythingapplication identifier.
 4. The method of claim 3, further comprisingdetermining the radio access type for transmitting avehicle-to-everything communication via direct vehicle-to-everythingcommunication based on a mapping of the vehicle-to-everythingapplication identifier corresponding to a vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications to aspecific radio access type.
 5. The method of claim 3, further comprisingdetermining the preemption of a first vehicle-to-everything applicationof the plurality of vehicle-to-everything applications based on amapping of the vehicle-to-everything application identifiercorresponding to the first vehicle-to-everything application to apreemption flag.
 6. The method of claim 5, further comprisingdetermining the cell that supports vehicle-to-everything resourcemanagement based on a vehicle-to-everything carrier frequency of thefirst vehicle-to-everything application of the plurality ofvehicle-to-everything applications.
 7. The method of claim 6, furthercomprising determining whether the cell supports vehicle-to-everythingresource management based on a vehicle-to-everything carrier frequencyof a second vehicle-to-everything application of the plurality ofvehicle-to-everything applications.
 8. The method of claim 7, furthercomprising determining that a second vehicle-to-everything applicationof the plurality of vehicle-to-everything applications cannot bepreempted and, in response to the cell not supportingvehicle-to-everything resource management based on thevehicle-to-everything carrier frequency of the secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications, selecting a different cell of theplurality of cells that supports vehicle-to-everything resourcemanagement and the carrier frequency of the second vehicle-to-everythingapplication.
 9. An apparatus comprising dual connectivity capability,the apparatus comprising: a processor that: establishes a firstplurality of network connections for direct communication with a mobilecommunication network and a second plurality of concurrent networkconnections for direct vehicle-to-everything communication with otherremote units over a plurality of radio access types, wherein theplurality of radio access types comprises evolved universal terrestrialradio access and new radio; receives a request to transmit avehicle-to-everything communication; determines whether thevehicle-to-everything communication is to be transmitted via a directcommunication with a mobile communication network or a directvehicle-to-everything communication with other remote units; determinesa radio access type of the plurality of radio access types fortransmitting the vehicle-to-everything communication via a directvehicle-to-everything communication; selects a cell of a plurality ofcells that supports vehicle-to-everything resource management for thevehicle-to-everything communication via a direct vehicle-to-everythingcommunication and the radio access type; and requests resources via thecell for transmitting the vehicle-to-everything communication via adirect vehicle-to-everything communication using the radio access type.10. The apparatus of claim 9, wherein the processor supports a pluralityof vehicle-to-everything applications, and each vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications usesa corresponding network connection of the second plurality of networkconnections for direct vehicle-to-everything communication with otherremote units over a corresponding radio access type of the plurality ofradio access types.
 11. The apparatus of claim 10, wherein eachvehicle-to-everything application of the plurality ofvehicle-to-everything applications has a vehicle-to-everythingapplication identifier.
 12. The apparatus of claim 11, wherein theprocessor determines the radio access type for transmitting avehicle-to-everything communication via direct vehicle-to-everythingcommunication based on a mapping of the vehicle-to-everythingapplication identifier corresponding to a vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications to aspecific radio access type.
 13. The apparatus of claim 11, wherein theprocessor determines the preemption of a first vehicle-to-everythingapplication of the plurality of vehicle-to-everything applications basedon a mapping of the vehicle-to-everything application identifiercorresponding to the first vehicle-to-everything application to apreemption flag.
 14. The apparatus of claim 13, wherein the processordetermines the cell that supports vehicle-to-everything resourcemanagement based on a vehicle-to-everything carrier frequency of thefirst vehicle-to-everything application of the plurality ofvehicle-to-everything applications.
 15. The apparatus of claim 14,wherein the processor determines whether the cell supportsvehicle-to-everything resource management based on avehicle-to-everything carrier frequency of a secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications.
 16. The apparatus of claim 15,wherein the processor determines that a second vehicle-to-everythingapplication of the plurality of vehicle-to-everything applicationscannot be preempted and, in response to the cell not supportingvehicle-to-everything resource management based on thevehicle-to-everything carrier frequency of the secondvehicle-to-everything application of the plurality ofvehicle-to-everything applications, selects a different cell of theplurality of cells that supports vehicle-to-everything resourcemanagement and the carrier frequency of the second vehicle-to-everythingapplication.